Improve range() return type for invalid steps and long ranges - #6492

Ref phpstan/phpstan#10022

Two inaccuracies in the return type of range():

1. An invalid $step makes range() throw a ValueError, but the extension still returned an array type. It now returns never when every combination of the constant arguments throws. PHP 7 returned false with a warning instead, so on PHP 7 it returns false. When the extension cannot decide a combination, the general type joins the types of the other combinations in the union.
2. For a range longer than RANGE_LENGTH_THRESHOLD the extension generalized the argument types, which predates the PHP 8.3 changes. It now generalizes the values the range consists of:

 // range('A', 'z')
-non-empty-list<int|(literal-string&lowercase-string&non-falsy-string)|(literal-string&non-falsy-string&uppercase-string)>
+non-empty-list<literal-string&non-empty-string>

 // range(1, 200, 1.0)
-non-empty-list<float>
+non-empty-list<int<1, 200>>

Since d52db07 the extension skips calling range() for a range longer than ARRAY_COUNT_LIMIT. On that path it applies the same rules to the argument types, and it rejects a negative $step on an increasing range on PHP 8.3+.

The extension folds the constant arguments by calling the native range(), so a caught ValueError only says that the runtime rejects the step. I gated both changes on PhpVersion $scope->getPhpVersion() wherever PHP 8.3 changed the behaviour, so conditions like PHP_VERSION_ID < 80300 narrow them. A $step of 0, or one wider than the range, has been a ValueError since PHP 8.0, unless both boundaries are equal and not both ints, while a negative $step on an increasing range and a non-finite $step only became one in 8.3. Before 8.3 an infinite $step failed as one wider than the range. An integral float $step produces ints since 8.3 and floats before that. Analysing for PHP 8.2 still gives non-empty-list<int> for range(2, 5, -1) and non-empty-list<float> for range(1, 200, 1.0). RangePhp82Test covers that axis: it sets phpVersion to 8.2 and runs on 8.3+. The tests in nsrt/ cover that axis with PHP_VERSION_ID conditions. The checks live in RangeFunctionArgumentsHelper, which this PR shares with #6539.

This does not close phpstan/phpstan#10022. PHPStan already infers the PHP 8.3 result for the reproducer in that issue, range('1', 'a'), because the extension folds the constant arguments through the native range(). For the same reason the folded values follow the PHP version PHPStan runs on rather than the configured phpVersion: with phpVersion: 80200 on a PHPStan running on 8.5, range('1', 'a') still comes out as the 49 element character range instead of array{1, 0}. Making the values follow phpVersion means reimplementing range() down to the rounding of start + i * step, and I did not want to put that in this PR. This PR fixes what you can decide without knowing the values: which steps PHP rejects, and how to generalize a range past the threshold.